Reports of 537 Clear search Modify search
Virgo Runs (VSR1)
mevans - 4:34 Thursday 20 September 2007 (18668) Print this report
(18658)
WOW! Great work finding this! This is a lesson for all future ITF designers.
Alignment (Alignment)
mevans - 17:16 Friday 29 June 2007 (17317) Print this report
(17310)
I‘m not sure if this helps, but remember that we investigated this in August (13075) and concluded that the glitches were being produced by the PZT, not the amplifier. A PZT with an over-constrained mounting can generate voltage glitches when it slips against the side constraints, and an ADC attached to the output of the amplifier box would see these glitches (since there is a resistor between the amplifier and the output of the box).
Good luck!
Virgo Runs (VSR1)
mevans - 16:54 Friday 22 June 2007 (17158) Print this report
(17149)
We never investigated carefully, but the 7:30am unlock (when the ITF was not so strong, it was an unlock) has been with us for a long time. We used to blame the cleaning girls, but then we started working until 8am and discovered that it is not their fault.
Virgo Runs (VSR1)
mevans - 19:40 Wednesday 13 June 2007 (16964) Print this report
(16962)
Will the Virgo+ input mirrors be wedged? If not, what are the implications for mirror thermal compensation? In particular, if the thermal compensator, which modifies the overall temperature of the mirror as well as the thermal lens, causes even larger temperature fluctuations than are currently present will alpha and beta still work? The frequency noise coupling also changes with the finesse asymmetry, but it is uncompensated...
Comments to this report:
punturo - 9:08 Thursday 14 June 2007 (16969) Print this report
Matt, we are aware of the problem and the first seed of the discusson is available in the last slide of the cited presentation: http://wwwcascina.virgo.infn.it/commissioning/weekly/2007/Jun2007/Etalon%20Effect%20in%20the%20Virgo%20cavities.ppt Further actions as soon as the problem will be completely understood.
Comments to this report:
bondu - 9:55 Thursday 14 June 2007 (16970) Print this report
About etalon effect: this effect is foreseen on purpose in Virgo, since the design, in order to be able to fine tune the the asymmetry for frequency noise through the finesse of the cavities. The frequency noise is negligeable now, and in the frequency region were it is not (~6kHz), the asymmetry is dominated by loss asymmetry, not finesse asymmetry.

The way to produce an error signal to measure and correct for finesse asymmetry: put a low frequency sine at f0 on frequency noise (f0 = a few 10s of Hz); detect it on dark fringe; demodulate at f0. The correction may be applicable to the tower temperature. The error signal would be a nice tower thermometer.

This solution should be applicable to Virgo, if needed, when we have the full resolution at low frequency, were the requirements for frequency stability should be the more stringent. There is no reason why we should not be able to do that in Virgo+, or Adv. Virgo, may be even with thermal compensation system for thermal lensing and parametric instability mitigation.
Comments to this report:
punturo - 12:46 Thursday 14 June 2007 (16974) Print this report
The hal-period of the thermal etalon effect is about 0.35 degrees. To have a thermal stabilization that suppress that effect we need currently to stabilize the temperature to about 0.1 degree. Difficult but still possible. In Virgo+, with a finesse 3 times larger, we will need probably a 3 times better temperature stabilization ... almost impossible. A more complex strategy must be designed, improving the AR coating specifications, stabilizing the temperature .... and having some new clever idea (if wedges cannot be used, as I suspect).
Comments to this report:
bondu - 15:15 Thursday 14 June 2007 (16982) Print this report
Let‘s assume that the etalon effect allow to divide the etalon fringe by 100. Then, using etalon, we actually measure "the" mirror temperature with a resolution of 0.003° ("the"=the one that determines the finesse asymmetry). Since the performances of a servo loop depend on the resolution of the error signal, there is no problem to servo the temperature at this level, even with an off/on system as correction. That‘s a much easier way to tune the asymmetry than to ask for identical coating reflectivities and hope for identical losses.
Comments to this report:
punturo - 16:54 Thursday 14 June 2007 (16985) Print this report
The SA is about 1 ton of steel, the tower have a thermal time constant of more than 10 hours, and it should be a little bit "difficult" to stailize it at 0.003 degrees while the environment temperature changes of about 1 degree.... A direct action on the mirror could be studied but it requires an integrated strategy (thermal compensation, coatings, ....). Let discuss it in a more appropriate environment (the next detector meeting)
Comments to this report:
brillet - 9:44 Friday 15 June 2007 (17000) Print this report
Francois is right : if the etalon effect is able to measure the effective temperature of the mirror (as concerns the etalon) , then we should be able to control it. This is the basic principle of all feedback loops. The limitation will come from the gain/bandwidth of the servo loop than we can implement, as compared to the open loop fluctuations.
The initial idea, that I proposed many years ago as a change request (!), was to put some heating tapes around the bottom part of the tower, to measure the etalon effect, evaluate the transfer function and hope to close a loop. This may be difficult because the time constant will not be much less than a day, but we can first reduce the day/night fluctuations with some feedforward, in order to request less gain from the servo-loop.
When a CO2 laser becomes available, it will be possible to heat directly the mirrors and the feedback will be quick enough. If we are smart, this can be done in parallel with the compensation of the lensing effect, by controlling independently the average power (etalon effect) and the geometry (thermal lens)
Length Sensing and Control (Frequency stabilization)
mevans - 20:55 Thursday 31 May 2007 (16644) Print this report
(16641)
Right. My mistake.
Length Sensing and Control (IMC length noise)
mevans - 17:14 Thursday 31 May 2007 (16640) Print this report
(16636)
The changes in Sa_MC_Gain_y_offs come from a loop in AlpInj which keeps MC_zCorrR around zero. I think the ramp is 30s long, and the maximum change is some 20um. I would be interested to know how these very slow "glitches" cause problems.
Length Sensing and Control (Frequency stabilization)
mevans - 17:07 Thursday 31 May 2007 (16638) Print this report
(16631)
Since the gain change is probably on the sensing side (i.e., the number of volts made on the IMC reflection sensor per Hz), and not on the actuation side (i.e., the number of Hz made per volt of drive to the laser), one SHOULD NOT change the SSFS pot to compensate for the 2dB attenuator. Please leave it where it was before (e.g., at 3.5).
Comments to this report:
bondu - 17:36 Thursday 31 May 2007 (16641) Print this report
The comment on the gain change for SSFS comes not from a guess or an intuition, but from equations, as explicited in a virgo note.

An other way to understand the need for gain change:
The slope of error signal (in V/Hz), in rampeauto, has decreased by 2 dB. One wants to add electronically a signal (SSFS_Corr) with similar V/Hz. The way to recover the cross-over between prestab and SSFS (at 20 kHz or so) is thus to decrease SSFS gain by a similar amount of 2 dB.

The SSFS open loop gain is:
G_ssfs = F_CARM*F_rack*T_IMC/F_IMC
where F_CARM is the TF between a frequency line before PR and demodulated signal on Pr_B5_ACp, F_rack the SSFS rack TF, T_IMC a low pass filter (pole of IMC), and F_IMC the IMC optical TF (=> cross-over with prestab).
Comments to this report:
mevans - 20:55 Thursday 31 May 2007 (16644) Print this report
Right. My mistake.
Injection system (General activities)
mevans - 17:18 Tuesday 29 May 2007 (16590) Print this report
(16587)
A 2dB reduction of the IMC loop gain should move the Laser/MC cross-over of the SSFS down by about 20% (nominally from 100 to 80 Hz). The cross-over has some margin, so a blind compensation would probably work. Measurement of the cross-over would be good, but I think the PROBES used for this measurement have been removed from the MC DSP card.
Global Control (Global Control)
mevans - 14:42 Tuesday 29 May 2007 (16584) Print this report
(16581)
Gc_Alpha_Out, when not being used for debugging, provides information about the difference between Gc_DARM_z and what is sent to the end mirrors (e.g., the alpha and beta corrections). That is,
Gc_Alpha_Out = alpha * alpha_filter * Gc_MICH_z + beta * Gc_PRCL_z
In case of problems with the alpha or beta corrections, or questions about what is added to the DARM correction (an important signal), this channel is critical.
Virgo Runs (VSR1)
mevans - 20:34 Monday 28 May 2007 (16564) Print this report
(16561)
The locking GainAdj flag currently only watches the DARM gain servo. It is sometimes red for the first few minutes in step 12 due to an excess of noise around the line at 379Hz, but after 10min in step 12 it should always be green. If, however, the noise level is high (horizon less than 3.5Mpc), the line may be lost and the flag will turn red. This is bad.

I have three suggestions:
1) increase the line DARM line amplitude by a factor of 2 until weather conditions are better (and horizon consistently > 3.5). I think the final line amplitudes are set in step 12.
2) modify the GainAdj flag to monitor also the MICH and PRCL gain servos
3) check the performance of the MICH and PRCL gain servos, and increase their line amplitudes if they are having trouble (both now 1.5e??, so change to 2.0??, for instance).

The GainAdj flag might currently use the max of the DARMline signal. I would suggest something more like the mean over 10 seconds, which should be less than 1.2 (for DARM, MICH and PRCL). This would allow for an occasional loss of coherence without making a red flag. A yellow flag condition could be set at a mean of 1.1.
Comments to this report:
Vajente - 23:13 Monday 28 May 2007 (16565) Print this report
Indeed during almost all the lock acquisitions of the run the flag has been red for several minutes even after reaching step 12. I didn‘t find any indication of misfunctioning of the UGF servos so far.
So I think that unless we notice something different today, we can safely ignore this flag for the first minutes of step 12.
Injection system (Laser power stabilization)
mevans - 12:33 Thursday 24 May 2007 (16488) Print this report
Pstab Glitches
To add a little more information to this problem: plot 1 shows that the Pstab error signal (Bs_IMC_D1T_DCHF) and the control signals (Bs_SL_Icorr_DC and DCHF) are coherent in frequency ranges where they are above ADC noise (about 3 uV/rtHz). Oddly, Sc_IB_TraMC looks little like D1T_DCHF, despite the fact that they should be the same signal with different filtering.

The second plot looks at TraMC and D1T_DCHF. TraMC goes quickly into the ADC noise, making it of little use, but at least one can see that D1T_DCHF appears to be an AC coupled version with a single zero at DC and a gain at 1Hz of about 100. One can also see that the spikes and discontinuitied in D1T_DCHF look quite odd... the experts have been contacted.
Images attached to this report
Comments to this report:
cleva - 13:43 Thursday 24 May 2007 (16490) Print this report
let ‘s call DPS the PHD used for Pstab located on IB:

Sc_IB_TraMC = 2.86W/V*DPS_DC (I am not sure 2.86W/V is up todate but it should not be very different)
Bs_IMC_D1T_DCHF = 56*DPS_AC*50 (factor 50 is applied in the Pstab rack, 56 is the transimpedance ratio between DC and AC channels)

(moreover Bs_IMC_D1T_DCHF is AC coupled with 16Hz cut-off)

plot 1 , at 10Hz Bs_IMC_D1T_DCHF=8e-4V/sqrt(Hz)
that should make 8e-4/56/50*2.86=8e-7V/sqrt(Hz) for Sc_IB_TraMC, well below ADC noise

plot 2, Sc_IB_TraMC=1e-4V/sqrt(Hz) @1Hz that should be
1e-4V/sqrt(Hz) /2.86*56*50*1/16 = 6e-3 V/sqrt(Hz)
on Bs_IMC_D1T_DCHF at 1Hz (measured 7e-3instead)

At least, in this regime those signals are coherent
Injection system (Laser power stabilization)
mevans - 20:22 Wednesday 23 May 2007 (16474) Print this report
Glitches in D1T_DCHF
Here are a bunch of plots. The message is that when the IMC relocks, Pstab can saturate, but this obvious saturation does NOT appear to be the cause of our noise bursts in science mode. There are, however, strange glitches in Bs_IMC_D1T_DCHF, which claims to be the IMC transmission (an thus the error signal for the Pstab loop)... but this signal looks a lot more like the IMC reflection (DC_DC) than the transmission (TraMC). In any case, the glitches in D1T appear as spikes in D4_DCHF, which can‘t be good.
Images attached to this report
Comments to this report:
cleva - 17:56 Thursday 24 May 2007 (16496) Print this report
for some comments, please see
http://wwwcascina.virgo.infn.it/commissioning/weekly/2007/May2007/Cleva_Pstab_230507.ppt
Interferometer_sensitivity_studies (General)
mevans - 16:27 Wednesday 23 May 2007 (16470) Print this report
Mystery Noise from Pstab?
As has been seen previously, our mystery noise has high and low phases. These phases can be easily seen in SSFS_Corr and SSFS_Visu, indicating that the noise source is likely in the laser lab (see first and second plots).

The more resolved plot 2 shows that the "high noise phase" (this one ending at 05:03:30 UTC) is characterizd by frequent short bursts, while in the low noise phase these bursts are much less frequent. Plots 3 and 4 show various signals that were not clearly related to our mystery noise. With plot 5, I found that Bs_SL_D2_RDCHF and D4_DCHF showed broad band bursts at the same time as SSFS_Visu.

Plots 6 shows these signals and the SL_Icorr_DC signals during the lock in science mode at the time of the change between high and low noise states. Plots 7 shows the signals as the ITF and IMC unlock, and the IMC relocks. Plot 8 is a higher resolution plot of the IMC relock (with the ITF unlocked), which shows that the noise bursts are present after the IMC relock and are visible as soon as the Pstab loop is enabled.

Further investigation is certainly necessary, but my preliminary conclusion is that we have a significant noise source associated with the Pstab loop. Disabling the loop has been seen to have negative effects, so we will have to work harder than that.
Images attached to this report
Global Control (Global Control)
mevans - 11:19 Wednesday 23 May 2007 (16466) Print this report
(16451)
Is there an entry indicating when these channels were added?
Virgo Runs (VSR1)
flaminio, ciardelli, mevans - 10:40 Wednesday 23 May 2007 (16465) Print this report
(16366)
This "fine tuning" involved:
1) removing 100kg which was rigidly attached to the Brewster
2) replacing 50kg, but sitting on a rubber pad

The original "hard" mount, which was aimed only at increasing the mass of the BW, was found not to be effective at reducing B1_ACp noise. The "soft" mount, on the other hand, was modestly effective in damping some mechanical resonances of the BW which were visible in B1_ACp (particularly 220Hz).
Alignment (Alignment)
mevans - 19:14 Tuesday 22 May 2007 (16457) Print this report
Q1p miscentering test
During the Q1p miscentering test, it was noted that the sensitivity degraded in the region of our mystery noise (200 to 800Hz, and 241Hz in particular). Looking at some other signals that are known to be coherent with B1_ACp in this region, we see that they did not change. This suggests that an offset in the Q1p changes the coupling of our mystery noise... maybe we can make a little test?
Images attached to this report
Interferometer_sensitivity_studies (General)
mevans - 17:59 Tuesday 22 May 2007 (16454) Print this report
SFP ramp
A quick look at the SFP PZT signals indicates that they are not coupling into the B1_ACp signal. There is also some indication of 10Hz harmonics... digital cameras?
Images attached to this report
Injection system (Mode cleaner autoalignment)
mevans - 19:12 Friday 18 May 2007 (16353) Print this report
IMC FF quadrant and the IBz signal
Last night around 1:30 am local, as part of our last minute noise hunting, I centered the IMC FF quadrant to remove coherence with SSFS_Corr. The coherence with IBz was near 1 when I started, and the DCh signal was near -0.1. When I finished the coherence was fluctuating, and the TF reduced by more than a factor of 10... the DCh signal was around 0.15. Similar numbers hold for the vertical centering.

Though this should have no effect on the AC alignment signal, in principal, there was a significant change in the IBz error signal. The result was a very slow drift of the IB (slow because the UGF of this loop is less than 100uHz) and an offset on the zCorr signal of about 0.6V.

To reduce the offset, after the work on the IB card this morning, I moved the Sa_IB_Gain_y_offs to 1150um. I also increased the servo gain (on the IBzAA.flt line) from 1e-5 to 1e-4, such that the loop converges in less than 1 hour (the noise is still very low, see plots).
Images attached to this report
Suspension Electronics (Suspension Electronic)
huet, hamdani, mevans - 15:52 Friday 18 May 2007 (16334) Print this report
MC mirror coils readout
As suggested by Matt, I had look to coil current of the MC mirror. First, with the help of R. Cavalieri we plugged the readout of the four coil drivers to an ADC of the C64 :
ADC4_4 : Up Coil
ADC4_5 : Down Coil
ADC4_6 : Left Coil
ADC4_7 : Right Coil
Slim modified the MC DSP card and for the time being, we can monitor only one coil at the same time. The probe name is Sc_MC_Coil_current and you can choose the coil you want to monitor by changing the corresponding gain in the DSP card.

We made a preliminary analysis when the MC was in High noise configuration (it should be said that the MC readout have no shaping filter). The first figure shows that what we measure is coherent with what we send when above ADC noise. The next four figures make the comparison between the measured coil current and the sent correction signal rescaled with driving factor, actuation factor and sensing factor. So we can say that ADC noise is around 5-6 uvolt/sqrt(Hrz) that is compatible with usual value.
Images attached to this report
Interferometer_sensitivity_studies (General)
mevans - 8:41 Friday 18 May 2007 (16329) Print this report
More Tapping in Central Building
We did more tapping tests, which can be summarized by: we tapped on WI, PR, and many connecting tubes, but we found nothing good. Occassional bursts of the 241/277 Hz noise could not be reproduced. A more detailed report will appear later, if meaningful.

The only clue comes form the PR seismometer... it has a nice line at our favorite frequency, 241 Hz. We tapped there, but got nothing special.
Images attached to this report
Global Control (Global Control)
barsotti, campagna, nenci, nemo, mevans - 7:45 Friday 18 May 2007 (16328) Print this report
Gc crash
The ITF unlocked from step 12 at 863485681, due to a Gc crash.
We had to stop and restart the locking process to recover..but we forgot to check the Gc elapsed time, which increased during this operation and the ITF unlocked again at step 10, during the NEO transition.

After that, the elapsed time seemed reasonable in await (64000), but at step 8 was too big, so we manually unlocked and we stopped and restarted the locking process a few times until the starting value was lower, around 62000.

After that we could reach science mode again.

As already reported, Matt added a protection in Alp, so that the locking sequence stops if the elapsed time is too high.

Of course it doesn‘t solve the problem, but at least reduces the wasted time,
which for us was at least 3 hours tonight...Nemo was not happy.
Images attached to this report
Injection system (General activities)
barsotti, mevans, vajente, nemo - 9:44 Thursday 17 May 2007 (16302) Print this report
Meglio fast che slow..
End of the long lock..
Images attached to this report
Comments to this report:
punturo - 13:05 Thursday 17 May 2007 (16308) Print this report
The IMC unlock trigger has been restored yesterday (and improved today) and it can be used to detect the (fast) unlocks of the IMC: http://wwwcascina.virgo.infn.it/commissioning/FastUnlock/ http://wwwcascina.virgo.infn.it/commissioning/FastUnlock/FastUnlock.html
Length Sensing and Control (Full ITF locking)
barsotti, mevans - 7:52 Thursday 17 May 2007 (16296) Print this report
Night Shift
Lock Acquisition
---------------------
The transition to B2_mix caused the unlock of the ITF twice today.
I increased the B2_mix gain to -0.0014, not clear if this helps.
(only 1 success after that (first plot)..ITF still locked.). To be checked.

Stability
----------
This night we tested some long term stability of the ITF.
The ITF remained locked for at least four hours twice (see second plot), and all the unlocks were due to "technical" problems.

Sensitivity
------------
The sensitivity is now worse than before below 70 Hz (third plot).
Looking at B1, the sensitivity was good on 16th May,
13h50 UTC, at the end of a lock, and bad at 17h31 UTC, after relocking at step 12 (fourth plot):

16/5 11:27 13:27 863350068 Science Mode 12 12 -
16/5 13:51 15:51 863358674 Adjusting Mode 12 12 -
16/5 14:14 16:14 863360074 Unlock! 12 12 173
16/5 15:56 17:56 863366203 Manual unlock 1 1 0
16/5 16:08 18:08 863366923 Manual unlock 1 1 0
16/5 16:16 18:16 863367413 Manual unlock 1 1 0
16/5 17:03 19:03 863370250 Unsuccessful locking attempt 12 11
16/5 17:30 19:30 863371842 Locked! 12 12


The noise budget shows that the noise goes through MICH (fifth plot).
Since we were sleeping at that time, we are quite confident not to be guilty :-)
The only operation reported in the log at that time is Calibration automation .

We checked if the alpha filtered was changed in between, but it doesn‘t look like it was. We don‘t find anything else to blame... but since this didn‘t change, what did?
Images attached to this report
Comments to this report:
swinkels - 14:58 Thursday 17 May 2007 (16312) Print this report
The alpha filter didn‘t change during that time, but its gain (Gc_Driving_MICH_NE-WE) did. During the afternoon, I switched the servo serveral times on and off and changed some things which have probably changed the set-point.
Interferometer_sensitivity_studies (General)
mevans - 7:46 Thursday 17 May 2007 (16297) Print this report
AlpDet::Oo_Align_Targets
I added a new feature to AlpDet which allows us to set the output bench alignment servo set-points to something other than zero (see AlpDet menu). I only tried x = 0.0 and y = 0.2. This was bad for the sensitivity, but did not change the 241 or 277 Hz peaks. Someone might try the other direction, or the beam position.
Images attached to this report
Interferometer_sensitivity_studies (General)
flaminio, mevans - 7:06 Thursday 17 May 2007 (16295) Print this report
Still Mystery Noise
We noted that our mystery noise has significant coherence with B1_DC and B2_DC, indicating that it is something which is seen by the ITF as power noise (see plots). I tried offsets on the MC mirror (giving SSFS_Corr a few volts mean value), and on the B1 PDs (+/- 400 counts on d2). Neither of these had any obvious effect.

Since the power after the MC is stabilized, one might wonder where these power fluctuations come from. Beam jitter is a possibility, but it would have to be jitter that the BMS does not see. We have also noted previously that the IMC quadrants AC and DC signals have some coherence with B1_ACp and SSFS_Corr.

The coherence of the IMC quadrant AC signals with SSFS_Corr (esp. IB_z, but also others) indicates that they are somewhat miscentered. We don‘t know what effect this has on our mystery noise, but one might hope that good centering (e.g., no coherence between SSFS_Corr and the IMC AC signals) would help to align the IMC. Fearing that moving motors on the injection bench will unlock the ITF, we leave this job to the next shift.
Images attached to this report
Search Help
×

Warning

×